Method and apparatus for a system management tool to adapt command interface and behavior based on installed features

ABSTRACT

A system management tool framework for a system management tool for extending system management commands related to software installation units such as software component, feature or product. The tool is constructed in accordance with an interface and framework that allows polymorphism and dynamic binding at run-time. When the system management software tool is constructed in accordance to the framework of the present invention, the software tool can be made scalable, flexible and adaptable to a heterogeneous distributed system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is filed concurrently with commonly assigned,non-provisional U.S. patent application Ser. No. (to be assigned),entitled “METHOD AND APPARATUS TO IMPLEMENT ADAPTIVE SCRIPTING TOOL”,listing as inventors Qinhua Wang, Lavena Chan, John Y. Chang, and MattRanjbar, having docket number IBM-No. AUS920040913US1

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention relates generally to the fields of computersoftware in a client-server heterogeneous distributed network.

2. Description of Related Art

A software product typically has various optional installable features.The software sometimes has system management commands or task commandsthat influence its runtime behavior or configuration properties. Forinstance, a task command “createApplicationServer” creates a newapplication server in the system. Another example is that a task command“startServer” starts a server in the system. More than often thebehavior of a system management command or task command provided asoftware product might need to be tuned based on which features usersdecide to install. For example, assuming a messaging software componentis an optional installation feature of an application server product,when users create an application server they can configure a messageengine on the created server only if the messaging component is alreadyinstalled. Another example is that one software product needs to extenda system management command of another related software product. Usingthe same example as in the previous scenario, when users create anapplication server, users can configure a portal container on thecreated server only if the portal product is already installed somewhereon the system. This scenario is similar to the previous one except itcrosses the product boundary and either resides on the local host orgoes somewhere else in the network.

A common solution to address the first scenario is that duringinstallation of the software, the software's command implementationqueries all the installed features present, and disables some of theinterfaces and/or logic on the software to be installed that are notavailable on the system or network. This solution however is notflexible and extensible. The command implementation needs to know allinstallation features and their relevance to the command. Whenever a newinstallable feature is introduced, the implementation of all therelevant commands need to be modified to accommodate the new installablefeature.

Furthermore, concerning the second example above involving a network,when the enhancement of a command crosses the product boundary, due tothe existence of a network, the above solution is no longer valid as itis very difficult for one software product to know whether all the othersoftware products and their installation features are on the same systemor network. Typically, therefore, the software product has to beprogrammed to provide a separate command for such heterogeneousdistributed network instances. This approach is not user friend, asusers need to learn additional command syntax for these distributedproducts. In addition, this approach is not flexible as theimplementation of this new command has a direct dependency on a commandof another software product.

Factoring all of the above, it can be seen that what is needed is asuperior method and apparatus for a system management tool, that isadapted to provide a command interface and behavior which is based onthe existence of installed features and products, in particular in aheterogeneous distributed system, without the necessity of programmersdeveloping and registering new commands every time a new softwareproduct is distributed in a network.

SUMMARY OF THE INVENTION

Accordingly, an aspect of the present invention is to provide animproved, scalable and flexible method and apparatus for a systemmanagement tool that is dynamically adaptable at runtime, via latebinding, abstract classes and inheritance, in a new IDL (InterfaceDefinition Language) framework, so that system management commands mayautomatically adapt their user interfaces and behavior based on thefeatures and products already installed on a system, which may includeaccess to a distributed system.

The framework of the present system management tool allows any optionalinstallable features and software products to register, implement andpackage new extensions of an existing system management command in aproduct. The extensions are packaged as part of installable features andsoftware products and these extensions are only activated whenever thefeatures and software products are installed.

Therefore, the mechanism of the present invention is not only extensiblebut also is flexible.

While in the preferred embodiment the software of the present inventionis directed to a system management tool, other types of software canalso be accommodated by the present invention without departing from theteachings of the present invention. For instance, any piece of softwareto be installed on a network can be made to fit inside a wrapper thatcan be deemed a system management tool, to aid in the installation ofthe software, and be accommodated by the teachings of the presentinvention.

The present invention employs system management software with a newInterface Definition Language (IDL) interface framework on both serverand client computer, for registering and instantiating new and existingsystem management commands, employing encapsulation, inheritance,polymorphism, and dynamic (late) binding at runtime, as part of a newapplication programming interface (API) framework, to increaseportability and scalability when distributing and executing new systemmanagement commands in a heterogeneous distributed network.

In a preferred embodiment, the method and apparatus of the presentinvention employs a mainframe or personal computer to run the softwaretool, but in general any compatible piece of hardware or virtual machinecan run the present invention.

Thus the preferred method and apparatus of the present invention is acomputing platform running a software tool, which can accept humaninput, and may be written in any computer language (such as C, C++,Perl, Java or the like), preferably an Object Oriented programming (OOP)language, run by a computer system having an operating system. Thecomputer system typically has one or more processors, primary andsecondary memory cooperating with the processor(s), which executesinstructions stored in the memory, I/O means such as monitor, mouse andkeyboard, and any necessary specialized hardware or firmware. Dependingon the language used to construct and implement the software tool, thesource code, object code and/or executables of the tool may have anynumber of classes, functions, objects, variables, templates, lines ofcode, portions of code and constructs (collectively and generally, “aprocess step”, “step”, “block”, “functional module” or “softwaremodule”) to carry out the invention in successive stages as describedand taught herein, and may be either a standalone software application,or employed inside of or called by another software application, or asfirmware. The software process or software module may be constructed sothat one portion of code in the application performs a plurality offunctions, as for instance in Object Oriented programming (e.g., anoverloaded process). The converse is also true, in that a plurality ofportions of code could perform a plurality of functions, and still befunctionally the same as a single portion of code. At any stage of theprocess step of the present invention, intermediate values, variablesand data may be stored for later use by the program. In addition, thebinary executable or source code data comprising the software of thepresent invention may reside on computer readable storage medium (e.g.,a magnetic disk, which may be portable, such as a hard drive), floppydrive; memory (e.g., flash RAM); or a DVD or CD-ROM disk).

The sum total of all of the above advantageous, as well as the numerousother advantages disclosed and inherent from the invention describedherein creates an improvement over prior techniques.

The above described and many other features and attendant advantages ofthe present invention will become apparent from a consideration of thefollowing detailed description when considered in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Detailed description of preferred embodiments of the invention will bemade with reference to the accompanying drawings. Disclosed herein is adetailed description of the best presently known mode of carrying outthe invention. This description is not to be taken in a limiting sense,but is made merely for the purpose of illustrating the generalprinciples of the invention. The section titles and overall organizationof the present detailed description are for the purpose of convenienceonly and are not intended to limit the present invention.

FIG. 1 is a schematic showing a heterogeneous distributed network in aclient-server relationship, within which the present invention resides.

FIG. 2 is a flowchart showing the steps necessary to build the frameworkarchitecture for the present invention.

FIG. 3 is a flowchart of the program flow for the present invention asconstructed within the framework described in FIG. 2.

It should be understood that one skilled in the art may, using theteachings of the present invention, vary the program flow of theflowcharts without departing from the spirit of the invention herein.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is to more readily register, instantiate, andconfigure system management type commands used in installing software ina heterogeneous distributed system, such as one having client andserver. Such system management commands are commands for software thatinfluence the software runtime behavior or configuration properties. Forinstance, a task command “createApplicationServer” creates a newapplication server in the system. Another example is that a task command“startServer” starts a server in the system. In a preferred embodimentthe present invention is built using Java, an object-orientedprogramming language, and the distributed system architecture is aclient-server model, but in general any programming language may beemployed and the network may be a peer-to-peer network, N-tierclient/server network, non-client—server model or other topology.

Turning now to FIG. 1, there is shown heterogeneous distributed networkin a client-server relationship, with the adaptive system managementtool of the present invention residing in both the client and server,and communicating via a suitable software interface protocol. A server,such as application-server 100, houses the server software portion ofthe software tool of the present invention, which is stored in thememory of the server. The server 100 communicates with several clients,120, 127, 129, 130 in a distributed network, typically a plurality ofpersonal computers, some of which may be connected together with a hubor router 125. In general the clients may be any computer system,personal computer, wireless devices, other server, and the like, formingwith the server 100 a heterogeneous distributed system network. Thesystem management software that resides in both the server and clientsis built according to the framework taught by the present invention.

An important aspect of the present invention is that it provides aframework of a unified architecture that delays the binding between thecommand interface and implementation—from developing time to run time—byencapsulating the system management commands a piece of systemmanagement software may have, via a language neutral command interface.This interface may also be termed, at the architecture level, a“protocol”, at the source code level “IDL” (Interface DefinitionLanguage), or, at the software component level, an “API” (ApplicationProgramming Interface) or “ABI” (Application Binary Interface). In apreferred embodiment, the command interface is defined in XML format dueto its programming language neutral nature and its flexibility fordynamic binding (late binding), which allows user-defined commands(“extensions” or “command extensions”, to existing system managementcommands) to be seamlessly integrated into a distributed network, asdescribed further herein. The key idea of this dynamic lazy bindingmechanism is generating the client side stubs (software routines thatprovide a common function) for commands dynamically, at run time, bycommunicating with a corresponding stub portion found on the serverinterface, by nature of the stubs being part of the same commonframework. This eliminates the need for clients to have command specificstatic stubs and prevents the potential complexities introduced by themismatch between client and server such as operating system, productversion, or product features differences.

In a preferred embodiment the object oriented language Java is employedto construct the software tool of the present invention, but in generalany language may be used.

Turning attention now to FIG. 2, there is shown a flowchart showing thesteps necessary to build the framework architecture for the systemmanagement tool of the present invention. As explained above, the goalis to provide a framework to implement a system management tool thatwill dynamically adapt a piece of software that is being installed on acomputer within a distributed network without the programmer or theprogram having any prior knowledge of what components need to be turnedon or present for the system management tool, except at run-time (i.e.,dynamic binding). The basic idea is to package an interface definition,description and implementation, so a system management tool thatconforms to this framework may allow a piece of software being installedin a system to dynamically discover (e.g., via late binding at runtime)all the available necessary components that need to be created and/orinstalled with the software in a distributed heterogeneous system,and/or to discover which features of the software being installed neednot be installed (i.e., turned off). Generally this command is termed a“system management command” of the system management tool, which is alsothe generic term for all such commands. Whenever a new installablefeature is introduced into software that is expanded or customized, andthis new feature requires additional functionality or command optionsnot found in an existing system management command, this new feature istermed a “extension” or “command extension” of a prior system managementcommand. Extensions often need additional information to be provided tousers, via help files, as explained further below.

For an example of the advantages of employing a common interface toallow dynamic binding, suppose that a developer of a piece of softwarehaving extensions (software capable of being expanded or customized)writes code so that the software can, as explained above, either havecertain features or components turned on when the software is installedin a network, and/or, have the software be configured a certain way onlywhen another software product is installed on the network. This behavioris termed a “conditional system management tool command” or “conditionalextension” of a command extension. Generally the software that is socontrolled by a command extension can be deemed “conditionallyactivated” software.

Thus if the conditionally activated extendible software is written to beextended within the framework as taught by the present invention, thedevelopers of all software that share this framework can write commandextensions to the software that cooperate with and conform to theframework through a common extension mechanism. With this commonextension mechanism, and suitably employing abstract classes andinheritance, as necessary (e.g., using the keyword ‘interface’ and‘extends’ in Java and ‘virtual’ in C++). any number of conditionalsystem management extensions can be bundled with installation featuresto either override some base system management command behavior orextend the base command interface for additional options based on theversion and features installed on the system. For example, the systemmanagement command can be a base class, and the extension commands canbe an inherited class (in C++) or the system management command can be asuperclass and the extension commands can be a subclass that inheritsfrom the superclass (in Object Oriented Programming parlance), generallytermed inherited classes. When the component or feature that providesthe command extension is installed, the behavior of the command willautomatically take the new component and feature into considerationwithout any user's intervention and knowledge, as the command request isrerouted to the command extension intelligently. Hence any commandrequest message from system management command object will be routedwithin the network to the proper command extension to handle that objectrequest.

Another scenario for conditionally activated software is that anoptional component and feature may allow users to provide additionaloptions specific to the component or feature. The present inventionallows one to capture the component and features and their additionalcommand options into command extensions, and bundles their commandextensions as part of its distribution package. Therefore, theseadditional command options that are specific to the component or featureare only visible to the end user when the component or feature isinstalled on the system.

Since this extension mechanism is completely dynamic and flexible thesame idea can be applied to across the product boundary. The only thingone needs to do is to replace the component or feature with anotherproduct. An example of this scenario is that a database product isinstalled on a system with the presence of a middleware applicationserver product on the same system. The database product may extend somesystem management commands of the application server product so that thesame command provided by the application server product can be used toconfigure the data access to the backend database. Assume if all theproducts on the same system use this extension mechanism, end users canconfigure their system end to end through a single familiar commandinterface. This would improve user experience and lower user's learningcurve significantly.

The polymorphism of the present invention allows, at runtime, theinterpreter and/or compiler, working with the operating system asnecessary, to automatically invoke the proper method associated witheach system management tool command and any instantiated objectassociated with the command, even though the same command name is usedfor many different versions of system management tools commands. In thisway, an end user invoking a system management tool command is obliviousto the fact that there may be several different versions of the samecommand. In is understood that in the present invention, which isimplemented by Java, when the term “compiler” or “interpreter” is used,that the term is used generically to refer to not only a Java nativelanguage machine compiler, but also a JIT (Just In Time) compiler, JavaVirtual Machine interpreter, or any other Java component to convertinstructions into machine code, including a hardware Java Chip, workingwith any necessary operating system and/or firmware of a computer.

Thus polymorphism in object oriented programming allows a generalizedrequest or function to produce different results based on the objectthat is attached to it at any given time. Furthermore, via inheritance,each extensible command (a command that is based upon a previouslydesigned base command) can inherit the properties of a base command itinherits from. The encapsulation afforded by polymorphism(late-binding), if a common interface is employed for all the systemmanagement software, as taught by the present invention, insures thatthe proper method for a particular command is called by a systemmanagement software program without the individual program having toseparately query the entire network it resides in on its own, assumingthe other programs are also written in this common framework. Finally,from the development side, a common framework eliminates the necessityfor the programmer to write separate functions for each particularversion of system management tool and then having to identify whichfeatures must be turned off when the tool is installed, or which othersoftware tools and products must be also installed on the network whenthe tool is installed. The software implemented by the framework of thepresent invention, and the compiler/interpreter running this software bynature of polymorphic OOP, automatically takes care of proper binding atrun-time (dynamic or late binding).

Thus, turning attention to FIG. 2, there is shown an apparatus flowchartfor a component, feature or product constructing command extensionsthrough the framework provided by the present invention. As a firststep, step 200 labeled “Define Interface for Base System Mng. Cmd.” thedeveloper of the system management tool of the present invention woulddefine the interface of the system management tool, and in particularthe interface of all the system management and task command steps andtheir implementation, and any dependent or inherited classes. Dependingon the language used and the state and layer of the data/source code,this interface could take the form of a protocol, IDL, API, abstractclass or superclass (a superclass in object technology is a high-levelclass that passes attributes and methods, down a hierarchy, tosubclasses, the classes below it), abstract or concrete superclasses;classes with inheritance and/or any combination of the above. In apreferred embodiment the framework is for the Java language.

As a second step, step 202 in FIG. 2 labeled “Implement the Cmd.Extension”, the developer of the system management tool of the presentinvention would implement the base system management command or taskcommand through a base class. This might be done in connection with apolymorphic class such as a virtual class, abstract class, orsuperclass, depending on the language. These base classes are associatedwith the interface to the protocol of step 200. Thus all systemmanagement commands, extensions of a system management command and allconditional extensions of system management commands have an inheritedclass (i.e. derived class) that may inherit from a base class associatedwith it.

From the teachings of the present invention, a component, feature orproduct can be allowed to provide a command extension or conditionalextension to override the behavior of a base class command extension.Likewise, the base command interface can be extended by an inheritedclass interface. By virtue of Object Oriented Programming, the systemmanagement tool of the present invention can have command interfaces andbehavior determined at run time through dynamic binding between theinterface and the implementation, when the implementation(s) areinstantiated.

In the third step, decision box 204 in FIG. 2,labeled “Declareextensions of base class?” the goal is to declare command extensions ofthe base system management commands have been accounted for; if so, oneproceeds to step 206, as indicated by the “Yes” branch of decision box204; if not, as indicated by the “No” branch of decision box 204, theflow continues to box 200 and the process repeats until all base classesand all extensions have been properly constructed according to the rulesof the framework, so that they work within a framework allowingpolymorphism as taught herein.

In step 206, labeled “Provide Help Info files with Extensions”, thecomponent, feature or product that provides command extensions throughthe framework for the tool of the present invention would providenational language supported (NLS) help files, in the form oftranslatable help messages, for each additional command extension, ifany additional command options are defined by the extension. Help filesare useful for both the developers and users of the tool, so they maylearn more about the system management command, extensions andconditional extensions via detailed descriptions of the commands.

In step 208, labeled “Implement the Cmd. Extensions”, the developers ofthe component, feature or product that provide the command extensionthrough the framework of the tool develop the logic of the commandextension following on the rules laid out by the framework.

In step 210, labeled “Package and Distribute Executables as part ofInstallable Product”, the tool of the present invention is distributedto all nodes as part of the relevant component, feature or productwithin the heterogeneous distributed network as a binary executable.

Turning attention now to FIG. 3, there is shown the program flow for themethod and product of the present invention, once all software productshave been constructed in accordance with the framework of FIG. 2.

Step 300 of FIG. 3 is to initialize the server and client nodes (in thepreferred client/server architecture as described herein). As apractical matter this would be done by each computer when it boots upand becomes aware of the network to which it is connected.

Step 305 in FIG. 3 occurs when the system management tool is launched,and discovers all the system management command, command extensions andconditional extensions dynamically, that is, through run-time (late)dynamic binding, a feature of polymorphism. Thus these extensions aremerged with the base command from which they are derived from, and madean integral part of the base command, as shown in FIG. 3, step 310. Suchmapping and binding is typically done by the compiler and/orinterpreter.

Concerning step 315 in FIG. 3, though polymorphism, it is not necessaryto map what extension goes to which necessary function call in thesystem management tool; rather, this is done by the interpreter and/orcompiler working in conjunction with the computer operating system, as afeature of polymorphism. Thus when the users of the present inventionexecute a system management command (or if it is executed automaticallyduring remote or automatic installation of a program), the mechanism ofthe present invention will intelligently route the request of thecommand to the proper extension implementation in the network, as shownin step 315 of FIG. 3. This intelligent routing can happen either withina node (computer) in the network, or, outside the boundaries of aparticular node (computer) in the network, and can map and routecomponents of software that may reside on other nodes (computers) in thenetwork.

Finally, assuming no exceptions that can be handled in the normal courseof the program, the program ends normally as per step 320.

Although the present invention has been described in terms of thepreferred embodiments above, numerous modifications and/or additions tothe above-described preferred embodiments would be readily apparent toone skilled in the art. For example, while in the preferred embodimentthe software of the present invention is directed to system managementsoftware, other types of software can also be accommodated by thepresent invention without departing from the teachings of the presentinvention. For instance, any piece of software can be made to fit insidea wrapper that can be deemed a system management tool, to both aid inthe installation of the software and /or to adapt the software to changeits interface and behavior based on installed features and products thatreside on a network into which the software is being introduced .

It is intended that the scope of the present invention extends to allsuch modifications and/or additions and that the scope of the presentinvention is limited solely by the claims set forth below.

1. A method of implementing, in a computer having memory, a system management application tool, said method comprising the steps of: defining a common interface for an application framework; implementing a plurality of system management commands; encapsulating each of said plurality of system management commands with said common interface, said system management commands cooperating with said interface; invoking said system management commands through said common interface of said application framework system of said management tool.
 2. The method as set forth in claim 1, further comprising the steps of: providing a plurality of computers in a distributed system to form a network; networking said plurality of computers together, said network having at least one client and a server; wherein each of said computers is associated with said common interface; said system management command having a client-portion residing on said client and a server-portion residing on said server; invoking said system management command by generating said client-portion dynamically, by allowing communication between said client-portion of said system management command and said server-portion of said system management command at run-time, by nature of said client-portion and server-portions being part of the same said framework.
 3. The method as set forth in claim 2, further comprising the steps of: implementing a command extension command to said system management command comprising a user-defined command; providing a detailed description of said user-defined commands, said detailed description in the way of help files programmably associated with said user-defined commands.
 4. The method as set forth in claim 3, further comprising the steps of: providing said help files with national language supported help, in the form of translatable help messages.
 5. The method as set forth in claim 2, further comprising the steps of: implementing a conditional extension command to said system management command, said conditional extension command comprising a command to control predetermined software in said network so said predetermined software is conditionally activated by said conditional extension command.
 6. The method as set forth in claim 1, further comprising the steps of: constructing an system management command object to associate with said system management command; binding said system management command object to computer memory dynamically, at run-time.
 7. The method as set forth in claim 6, further comprising the steps of: constructing said application framework in the Java language.
 8. The method as set forth in claim 6, further comprising the steps of: providing a plurality of computers in a distributed system to form a network; networking said plurality of computers together, wherein each of said computers is associated with said common interface.
 9. The method as set forth in claim 8, further comprising the steps of: implementing a user-defined command extension to said system management command comprising a command defined by a user to an existing set of system management commands; wherein said command extension and said system management command are in a program neutral language format comprising XML format.
 10. The method as set forth in claim 8, further comprising the steps of: implementing a conditional extension command to said system management command, said conditional extension command comprising a command to control predetermined software in said network so said predetermined software is conditionally activated by said conditional extension command; wherein said conditional extension and said system management command are in a program neutral language format.
 11. A computer readable storage medium storing software data in the form of computer code, comprising: a common interface software module for an application framework; a system management command software module for providing task commands to software that influence software runtime behavior and configuration properties; said common interface software module and said system management command software module cooperating with one another and written in a Object Oriented Programming (OOP) language; and, said common interface software module written in a programming neutral format.
 12. The invention according to claim 11, wherein: said common interface software module neutral format is XML format; said OOP language is Java.
 13. The invention according to claim 12, wherein: said system management command software module has a client portion stub module and a server portion stub module, said client and server portions stubs constructed to be bound and associated with one another dynamically at run-time.
 14. An apparatus for constructing a system management tool, for implementation in a computer, comprising: an application development program framework for operation in a computer; said application development program framework comprising a common interface object for said application framework; and, a system management command object operatively connected with said common interface object of said framework.
 15. The apparatus according to claim 14 wherein: said framework constructs said objects in an object oriented programming language, said framework constructs said objects as binary executable code, and said objects are constructed to allow dynamic binding of the binary executable code at run-time.
 16. The apparatus according to claim 15 wherein: said system management command object has a base class and at least one inherited class derived from the base class.
 17. The apparatus according to claim 16 wherein: said system management command inherited class is a class for a conditional extension command to allow software to be conditionally activated through said command.
 18. The apparatus according to claim 16 wherein: said system management command inherited class is a class for a user-defined command extension, said command extension programmably associated with help files, said help files including national language support.
 19. The apparatus according to claim 16 wherein: said framework object oriented programming language is Java; said common interface is written in a programming neutral format, and said system management command object is written in language comprising the XML format.
 20. A system for implementing a system management tool in a distributed system, comprising: a plurality of computers in a distributed system forming a network; a common interface software module for an application framework forming a common interface for said application framework, each of said computers associated with said common interface; a plurality of system management command software modules for implementing system management commands, said plurality of system management software modules reside in said computers in said network; wherein said system management command software modules communicate with said common interface software module of said application framework and are encapsulated by said common interface software module of said application framework.
 21. The invention according to claim 20 further comprising: said network comprises at least one client and a server; said system management command modules are comprised of system management command objects; said system management command module has a client-side object residing on at least one client and a server-side object residing on said server; said objects are constructed to allow dynamic binding of the client object when said client-side object is instantiated at run-time.
 22. The invention according to claim 21, wherein: said system management command is written in an Object Oriented Programming language; said system management command object has a base class and at least one inherited class derived from the base class;
 23. The invention according to claim 22 wherein: said system management command inherited class is a class for a conditional extension command to allow software to be conditionally activated through said command.
 24. The invention according to claim 22 wherein: said system management command inherited class is a class for a user-defined command extension, said command extension programmably associated with help files, said help files including national language support.
 25. The invention according to claim 24 wherein: said framework object oriented programming language is Java; said common interface is written in a programming neutral format, and said system management command object is written in language comprising the XML format.
 26. The invention according to claim 22 further comprising: a compiler for said framework; said system management command objects having a command request message corresponding to a command request query and a command extension corresponding to the query; said compiler routing said command request message to the command extension dynamically.
 27. The invention according to claim 26 further comprising: said system management command inherited class is a class for software to be conditionally activated through said command.
 28. The invention according to claim 26 wherein: said system management command inherited class is a class for a user-defined command extension, said command extension programmably associated with help files, said help files including national language support.
 29. The invention according to claim 26 wherein: said framework object oriented programming language is Java; said common interface is written in a programming neutral format, and said system management command object is written in language comprising the XML format. 